Skip to content

fix: advertise the current package version to MCP clients#21

Closed
cybercraftsolutionsllc wants to merge 1 commit into
eliottreich:mainfrom
cybercraftsolutionsllc:codex/server-version-14
Closed

fix: advertise the current package version to MCP clients#21
cybercraftsolutionsllc wants to merge 1 commit into
eliottreich:mainfrom
cybercraftsolutionsllc:codex/server-version-14

Conversation

@cybercraftsolutionsllc

Copy link
Copy Markdown

Fixes #14.

Summary:

  • move the package/server version into a small shared module
  • use that same server info object for the MCP Server initialize metadata
  • add a node:test regression that compares the advertised server version against package.json

Validation:

  • npm ci --ignore-scripts
  • npm test
  • git diff --check

Payout route if needed: 0xB34D185318b34ec2F9E060F662Cc7feA3180049c

@eliottreich

Copy link
Copy Markdown
Owner

Closing as superseded: the server now advertises the real package version (PKG_VERSION) to MCP clients on main. Thanks for the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

MCP server advertises wrong version (0.1.0) to clients

3 participants